Rest API Rate Limit

#1

Hi,

Here is documentation regarding rate limit:https://v2.developer.pagerduty.com/docs/rate-limiting.

Following are the questions

  1. What does “If your client is throttled, its rate limit will be reset after a minute interval. Your client should expect and be able to handle this error code by waiting a minute before making additional requests.” exactly mean? Can you explain in detail with an example?

  2. What is the exact rate limit in terms of API calls? How many GET , POST, PUT API calls are allowed?

  3. Is there any way to overcome this limit? if yes, how?

Thank You

Regards,

#2
  1. The client/software you use to make API calls should be able to utilise a “retry” logic when you receive the rate limit error codes. We don’t have examples for this because there are many and varied ways to interact with our API, but you should be able to consult the developer of the client you use.
  2. It depends on the API –

Events - 120/min/integration key (60 for email integrations). Enforced at the per-integration-key level.

REST API - up to 2,000/min per key
Incident Create API is heavily rate limited - 1 event/second. Rate limit is intended for “human speed”

Global Routing - 120/min/integration key

  1. Our rate limits are subject to change but we cannot make individual exceptions for them.
#3

Hi ,

So ,

  1. Let’s say my rate limit is exceed then will it be automatacally retried after 1 minute or do we need to retry it?
  2. so Get requests are 2000/min per authentication key and 60/min POST requests per authentication key
  3. is there any way to change the rate limit from API request?

Thank You

Regards,

#4

Hi @Sonal1,

  1. If you are rate limited, the event is dropped. As Tom stated, you should apply your own retry logic; it is recommended to take note of the response code that is returned from your request for this reason.
  2. No, not quite - these are cumulative limits for all requests (POST, PUT, and GET)
  3. No, these are hard limits, so we are unable to change them.